[v 2.3.0] RUBY-1104 Add CursorReaper for periodically sending kill cursor operations #766
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Todo:
Consolidate cursor ids into one op per namespace + server in CursorReaper#kill_cursors(not going to do thisUse read_with_one_retry method instead of read_with_retry (in sep PR right now)Must add disconnect method to CursorReaperCheck if cursor is active at time of sending kill cursors op instead of when it is scheduled